chore(ci): annotate release runs with version#40
Conversation
Adds a notice annotation and step-summary line right after `changeset version` so the released version is visible at the top of the Actions run without drilling into step logs. Includes a `(dry run)` suffix when the workflow is dispatched with `dry-run=true`.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #40 +/- ##
=======================================
Coverage ? 95.73%
=======================================
Files ? 53
Lines ? 2488
Branches ? 423
=======================================
Hits ? 2382
Misses ? 106
Partials ? 0 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
1 participant
Summary
Surfaces the release version at the top of every Release workflow run as a GitHub Actions notice annotation and a one-line step summary, so you don't have to drill into the logs to see which version a given run produced.
Changes
Annotate release versionstep in.github/workflows/release.yml, placed immediately afterVersion packages(when the version is definitively known).::notice title=Release version::v<x.y.z>and appends## Release v<x.y.z>to$GITHUB_STEP_SUMMARY.(dry run)to both when the workflow is dispatched withdry-run=true.Testing
Hard to test without dispatching the workflow. On the next Release run (or a
dry-run=truedispatch), the run page should show a "Release version: v0.X.Y" banner at the top and a matching header in the Summary panel.No changeset —
chore/branches are exempt from thechangesetCI gate (see.github/workflows/main.yml:13).